2016-07-13 - 27620 - Spec - Internal Order IDOC setup for Concur #MMPPSupport

SPECIFICATIONS

27620 - Spec - Internal Order IDOC setup for Concur


Purpose


Internal Order IDOC setup for Concur.

Admin Info


Purpose
Internal Order IDOC setup for Concur
Requested By
Babu Lankipalli
Spec Created By
Laxman
Spec Created Date
10/31/2016
Spec QA by
Laxman
Objects
Basic type: INTERNAL_ORDER01
Message Type: INTERNAL_ORDER
Document Status
Complete

Estimates


Sl.No
Activity
Estimation in Hours
1
Research
08
2
Documentation
04
3
Development/ Config
12
4
Unit test in DEV
04
5
Unit test in QUA
04
6
Other activity


TOTAL
32
References

Prior Tickets

[Provide links of prior associated Spec / Break Fix BOSS document(s)]

Documents

[Attach any document(s) received for the requirement(s)]

Spec Changes


[List the changes made to program after the approval of the original requirement along with the Date on which the change request was received and the name of the initiator]

Sl.
Change Details
Requested By
Requested On
Notes if any
01
Naming convention should be
different for Statistical Internal orders
Babu Lankipalli
12/02/2016

Functional Requirement


Purpose/WHY:

[Explain the purpose of the project and the reason why this requirement has come]
Since employee travelling expenses are settled against Internal Order, Concur required updated information of Internal Orders.

In Scope:

[List the activities to be included in scope]

Out of Scope:

[Out of scope activities]

Solution Summary


[Discuss this section with Requester and get approval prior to beginning work]


Understand that, travelling expenses of few employee are settled against corresponding Internal Orders. Since Concur is using to calculate and settle the travelling expenses, updated Internal Order information is required in the Concur. So to full fill this requirement decided to send the data of Internal Order using below given IDOC type. Using this IDOC both newly created Internal Order and their changes can be forwarded to Concur.
Basic Type: INTERNAL_ORDER01
Message Type: INTERNAL_ORDER

DT: 12/02/2016
For statistical internal orders naming convention should be List_ p0026220wx6o_YYYYMMDDHHSS

Test Plan

[List test scenarios/cases to be executed here]
Test ID
Test Scenario
Expected Results
MM001
Create the Internal order using document type ZNEC
IDOC with Internal order data will be triggered without any errors
MM002
Change the Internal order of document type ZNEC
IDOC with Internal order data will be triggered without any errors

DT: 12/02/2016
Test ID
Test Scenario
Expected Results
MM003
Create the statistical Internal order using document type ZNEC
IDOC will be triggered without any errors and name format should be
List_ p0026220wx6o_YYYYMMDDHHSS
MM004
Change the statistical Internal order of document type ZNEC
IDOC will be triggered without any errors and name format should be
List_ p0026220wx6o_YYYYMMDDHHSS
Solution Details
[Provide complete technical details for configuration or programming here]

Complete the IDOC setup to forward the Internal Order data to Concur from SAP.

Issues


[List Issues / Bugs identified in configuration or development]